Skip to main content
Huỳnh Thanh Nhàn
💬
0 discussions

ENV

I. Env Table

Link To Env File


NameLineChain
LOGSTASH_DOMAINsrc/config/elastic.js:13
LOGSTASH_USERNAMEsrc/config/elastic.js:17
LOGSTASH_PASSWORDsrc/config/elastic.js:18
USERNAMESsrc/lib/auth.js:13
PASSWORDsrc/lib/auth.js:13
ACCESS_SERVICE_HOSTsrc/lib/access.js:7
ACCESS_SERVICE_KEYsrc/lib/access.js:11
ACCESS_SERVICE_SECRETsrc/lib/access.js:12
ES_DOMAINsrc/config/elastic.js:7
ES_USERNAMEsrc/config/elastic.js:7
ES_PWDsrc/config/elastic.js:7
PORTsrc/index.js:37

II. Quick List


  • Public:

  • Dev:

https://gitlab.com/gcalls-opensource/secrets/gcallsenv/-/blob/master/envLocal/pbx-service.env
  • Test:

  • Prod:

https://gitlab.com/gcalls-opensource/secrets/gcallsenv/-/blob/master/envCloud/pbx-service.env
https://gitlab.com/gcalls-opensource/secrets/gcallsenv/-/blob/master/envXR/pbx-service.env

III. Ticket Table



IV. Flow List


    git clone https://gitlab.com/gcalls-opensource/secrets/gcallsenv.git
  • Search and note where to use environment variable in Customer Service
  • Clone Project:
    git clone https://gitlab.com/gcalls-opensource/publics/gcallsback/-/tree/Test/streamService
  • Search and note ticket should change, fix, refactor, research or implement for better env-based productivity development and system performance in Gcalls Issues